Light ROM 4/Light ROM 4 - Disc 1.iso/text/maillist/1996/030196.doc/[e-mail] _Wed Mar 6 18:31:12 1996.msg

Internet Message Format | 1996-03-09 | 2KB

Received: from mail.webcom.com (mail.webcom.com [206.2.192.68]) by keeper.albany.net (8.7.4/8.7.4-MZ) with ESMTP id SAA11058 for <[e-mail]>; Wed, 6 Mar 1996 18:31:11 -0500 (EST)
Received: from localhost by mail.webcom.com with SMTP
    (1.37.109.15/16.2) id AA176315012; Wed, 6 Mar 1996 15:30:12 -0800
Date: Wed, 6 Mar 1996 15:30:12 -0800
Errors-To: [e-mail]
Message-Id: <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Originator: [e-mail]
Sender: [e-mail]
Precedence: bulk
From: James Jones/Nibbles and Bits <[e-mail]>
To: [e-mail]
Subject: Call For Suggestions
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Status: RO
X-Status:

[e-mail] said:

>    OK, I'm making an logo treatment that deals with a cloud of
>objects, maybe a couple of hundred, that eventually coallesce to
>form the logo.
>
>    I've got a couple of ideas on how to approach this, mainly using
>Sparks(tm), but am curious as to how various members of the LWMList would
>approach this situation.

   If your objects (200? GAK!) don't have to rotate, bounce, or fly
along curved trajectories on their way to the logo, and if it's OK for
them to arrive at the logo shape in unison, then an object with all the
parts in their cloud positions morphed to an object with 'em all in
their logo positions might save a bit of work. (Assuming you could use
some automated way of positioning the parts in Modeler, such as particle
clone.)

   Other than that, a backward-rendered Sparks scene sounds like the
way to go.

   -Jim

James G. Jones
Nibbles & Bits
[e-mail]
__